View LAN8187-JT_3896299.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

smsc lan8187/lan8187i datasheet revision 0.6 (02-24-06) datasheet product features lan8187/lan8187i high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix ? single-chip ethernet physical layer transceiver (phy) ? performs hp auto-mdix in accordance with ieee 802.3ab specification ? automatic polarity correction ? comprehensive smsc flexpwr tm technology ? flexible power management architecture ? lvcmos variable i/o voltage range: +1.6v to +3.6v ? integrated 3.3v to 1.8v regulator for optional single supply operation. ? regulator can be disabled if 1.8v system supply is available. ? energy detect power-down mode ? low current consumption power down mode ? low operating current consumption: ? 39ma typical in 10base-t and ? 79ma typical in 100base-tx mode ? 8kv hbm esd performance ? supports auto-negotiation and parallel detection ? supports the media independe nt interface (mii) and reduced media independent interface (rmii) ? compliant with ieee 802.3-2005 standards ? mii pins tolerant to 3.6v ? ieee 802.3-2005 compliant register functions ? integrated dsp with adaptive equalizer ? baseline wander (blw) correction ? vendor specific register functions ? low profile 64-pin tqfp package; green, lead-free ? 4 led status indicators ? commercial operating temperature 0 c to 70 c ? industrial operating temperature -40 c to 85 c version available (lan8187i) applications ? set top boxes ? network printers and servers ? lan on motherboard ? 10/100 pcmcia/cardbus applications ? embedded telecom applications ? video record/playback systems ? cable modems/routers ? digital video recorders ? personal video recorders ? ip and video phones ? wireless access points ? digital televisions ? digital media adapters/servers ? pos terminals ? automotive networking ? gaming consoles ? security systems order number(s): LAN8187-JT for 64-pin, tqfp package (green, lead-free) lan8187i-jt for industrial temperature 64-pin, tqfp package (green, lead-free)
80 arkay drive hauppauge, ny 11788 (631) 435-6000 fax (631) 273-3123 copyright ? 2006 smsc or its subsidiaries. all rights reserved. circuit diagrams and other information relating to smsc produc ts are included as a means of illu strating typical applications. consequently, complete information sufficient for construction purposes is not necessarily given. although the information has been checked a nd is believed to be accurate, no responsibility is assumed for inaccuracies. smsc reserves the right to make changes to specifications and product descriptions at any time without notice. contact your local smsc sales office to obtain the latest specifications before placing your product order . the provision of this information does not convey to the purchaser of the described semiconductor devices any licenses under any patent rights or oth er intellectual property rights of smsc or others. all sales are expressly conditional on your agreement to the terms and conditions of the mos t recently dated version of smsc's standard terms of sale agreement dated before the date of your order (the "terms of sale agreement"). the pro duct ma y contain design defects or errors known as anomalies which may cause the product's functions to deviate from published specifica tions. anomaly sheets are available upon request. smsc products are not designed, intended, authorized or warranted for use in any life suppor t or othe r application where product failure could cause or contribute to personal injury or severe property damage. any and all such uses without prior written approval of an officer of smsc and further testing and/or modification will be fully at the risk of the customer. copies of thi s document or othe r smsc literature, as well as the terms of sale agreement, may be obtained by visiting smsc?s website at http://www.smsc.com. sms c is a registered trademark of standard microsystems corporation (?smsc?). product names and company names are the trademarks of their respective holders. smsc disclaims and excludes any and all warranties, including without limitation any and all implied warranties of merchantability, fitness for a particular purpose, title, and against infringement and the like, and any and all warranties arising from any course of dealing or usage of trade. in no event shall smsc be liable for any direct, incidental, indirect, special, punitive, or consequential damages; or for lost data, profits, savings or revenues of any kind; regardless of the form of action, whether based on contract; tort; negligence of smsc or others; strict liability; breach of warranty; or otherwise; whether or not any remed y of buyer is held to have failed of its essential purpose, and whether or not smsc has been advised of the possibility of such damages. high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 2 smsc lan8187/lan8187i datasheet
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 3 revision 0.6 (02-24-06) datasheet table of contents chapter 1 general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 architectural overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 chapter 2 pin configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 package pin-out diagram and signal table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 chapter 3 pin description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1 i/o signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 chapter 4 architecture details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.1 top level functional architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.2 100base-tx transmit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.2.1 100m transmit data across the mii/rmii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.2.2 4b/5b encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.2.3 scrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.2.4 nrzi and mlt3 encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.2.5 100m transmit driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.2.6 100m phase lock loop (pll) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.3 100base-tx receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.3.1 100m receive input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.3.2 equalizer, baseline wander correction and clock and data recovery . . . . . . . . . . . . . 21 4.3.3 nrzi and mlt-3 decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.3.4 descrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.3.5 alignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.3.6 5b/4b decoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.3.7 receive data valid signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 4.3.8 receiver errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.3.9 100m receive data across the mii/ rmii interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.4 10base-t transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.4.1 10m transmit data across the mii/rmii interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.4.2 manchester encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.4.3 10m transmit drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.5 10base-t receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.5.1 10m receive input and squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.5.2 manchester decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.5.3 10m receive data across the mii/rmii interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.5.4 jabber detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.6 mac interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.6.1 mii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.6.2 rmii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.6.3 mii vs. rmii configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 4.7 auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4.7.1 parallel detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.7.2 re-starting auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 9 4.7.3 disabling auto-negotiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.7.4 half vs. full duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.8 hp auto-mdix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.9 internal +1.8v regulator disa ble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.9.1 disable the internal +1.8v regulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.9.2 enable the internal +1.8v regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.10 (tx_er/txd4) /nint strapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 4 smsc lan8187/lan8187i datasheet 4.11 phy address strapping and led output polarity selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.12 variable voltage i/o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.12.1 boot strapping configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.12.2 i/o voltage stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.13 phy management control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.13.1 serial management interface (smi). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 chapter 5 registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.1 smi register mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 5.2 smi register format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 5.3 interrupt management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.4 miscellaneous functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.4.1 carrier sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.4.2 collision detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.4.3 isolate mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.4.4 link integrity test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.4.5 power-down modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 0 5.4.6 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 5.4.7 led description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 5.4.8 loopback operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 5.4.9 configuration signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 chapter 6 electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 6.1 serial management interface (smi) timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 6.2 mii 10/100base-tx/rx timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 6.2.1 mii 100base-t tx/rx timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 6.2.2 mii 10base-t tx/rx timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 6.3 rmii 10/100base-tx/rx timings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 6.3.1 rmii 100base-t tx/rx timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 6.3.2 rmii 10base-t tx/rx timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 6.4 ref_clk timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 6.5 reset timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 6.6 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6.6.1 operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6.6.2 power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6.6.3 dc characteristics - input and output buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 chapter 7 package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 5 revision 0.6 (02-24-06) datasheet list of figures figure 1.1 lan8187/lan8187i system block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 1.2 lan8187/lan8187i architectural overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 2.1 package pinout (top view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 4.1 100base-tx data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 4.2 receive data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 figure 4.3 relationship between received data and specific mii signals . . . . . . . . . . . . . . . . . . . . . . . 22 figure 4.4 direct cable connection vs. cross- over cable connection.. . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 4.5 phy address strapping on led?s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 figure 4.6 mdio timing and frame structure - read cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 4.7 mdio timing and frame structure - write cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 6.1 smi timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 figure 6.2 100m mii receive timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 figure 6.3 100m mii transmit timing diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 figure 6.4 10m mii receive timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 figure 6.5 10m mii transmit timing diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 figure 6.6 100m rmii receive timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 6.7 100m rmii transmit timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 figure 6.8 10m rmii receive timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 figure 6.9 10m rmii transmit timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 6.10 reset timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 figure 7.1 64 pin tqfp package outli ne, 10x10x1.4 body, 12x12 mm footprint . . . . . . . . . . . . . . . . 66
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 6 smsc lan8187/lan8187i datasheet list of tables table 2.1 lan8187/lan8187i 64-pin tqfp pinout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 table 3.1 mii signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 table 3.2 led signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 3.3 management signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 3.4 boot strap configuration inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 3.5 general signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 3.6 10/100 line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 3.7 analog references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 3.8 no connect signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 3.9 power signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 4.1 4b/5b code table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 4.2 mii/rmii signal mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 4.3 boot strapping configuration resistors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 5.1 control register: register 0 (basic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 5.2 status register: register 1 (basic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 5.3 phy id 1 register: register 2 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 5.4 phy id 2 register: register 3 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 5.5 auto-negotiation advertisement: register 4 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 5.6 auto-negotiation link partner base page ability register: register 5 (extended) . . . . . . . . . 35 table 5.7 auto-negotiation expansion register: register 6 (e xtended). . . . . . . . . . . . . . . . . . . . . . . . . 35 table 5.8 auto-negotiation link partner next page tran smit register: register 7 (extended) . . . . . . . 35 table 5.9 register 8 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.10 register 9 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.11 register 10 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.12 register 11 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.13 register 12 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.14 register 13 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 5.15 register 14 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 5.16 register 15 (extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 5.17 silicon revision register 16: vendor-specific. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 5.18 mode control/ status register 17: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 5.19 special modes register 18: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 7 table 5.20 reserved register 19: vendor-specific. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 5.21 register 24: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 5.22 register 25: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 5.23 register 26: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 5.24 special control/status indicati ons register 27: vendor-specific . . . . . . . . . . . . . . . . . . . . . . 38 table 5.25 special internal test ability control register 28: vendor-specific . . . . . . . . . . . . . . . . . . . . . . 39 table 5.26 interrupt source flags register 29: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 5.27 interrupt mask register 30: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 5.28 phy special control/status register 31: vendor-specific . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 5.29 smi register mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 5.30 register 0 - basic control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 5.31 register 1 - basic status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 5.32 register 2 - phy identifier 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 5.33 register 3 - phy identifier 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 5.34 register 4 - auto negotiation adve rtisement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 5.35 register 5 - auto negotiation link partner ability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 table 5.36 register 6 - auto negotiation expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 5.37 register 16 - silicon revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 5.38 register 17 - mode control/status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 5.39 register 18 - special modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 5.40 register 27 - special control/status indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 7 revision 0.6 (02-24-06) datasheet table 5.41 register 28 - special internal te stability controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 5.42 register 29 - in terrupt source flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 5.43 register 30 - in terrupt mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 5.44 register 31 - phy special control/status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 5.45 mode[2:0] bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 table 6.1 smi timing values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 6.2 100m mii receive timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 6.3 100m mii transmit timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 6.4 10m mii receive timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 table 6.5 10m mii transmit timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 table 6.6 100m rmii receive timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 table 6.7 100m rmii transmit timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 table 6.9 10m rmii transmit timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 6.10 ref_clk timing values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 6.8 10m rmii receive timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 6.11 reset timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 6.12 power consumption device only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 6.13 mii bus interface signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 table 6.14 lan interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 6.15 led signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 6.16 configuration inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 6.17 general signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 6.18 analog references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 6.19 internal pull-up / pull-down config urations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 6.20 100base-tx transceiver characterist ics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 table 6.21 10base-t transceiver char acteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 table 7.1 64 pin tqfp package parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 8 smsc lan8187/lan8187i datasheet chapter 1 general description the smsc lan8187/lan8187i is a low-power, industrial temperature (lan8187i), variable i/o voltage, analog interface ic with hp auto-mdix for high-performance embedded ethernet applications. the lan8187/lan8187i can be confi gured to operate on a single 3. 3v supply utilizing an integrated 3.3v to 1.8v linear regulator. an option is availabl e to disable the linear regulator to optimize system designs that have a 1.8v power plane available. 1.1 architectural overview the lan8187/lan8187i consists of an encoder/decoder, scrambler/descrambler, wave-shaping transmitter, output driver, twisted-pair receiver with adaptive equalizer and baseline wander (blw) correction, and clock and data recovery functions . the lan8187/lan8187i can be configured to support either the media independent interface (m ii) or the reduced media independent interface (rmii). the lan8187/lan8187i is compliant with ieee 802.3-2005 standards (mii pins tolerant to 3.6v) and supports both ieee 802.3-2005 -compliant and vendor-specific register functions. it contains a full- duplex 10-base-t/100base-tx transceiver and supports 10-mbps (10base-t) operation on category 3 and category 5 unshie lded twisted-pair cable, and 100-mbps (100base-tx) operation on category 5 unshielded twisted-pair cable. figure 1.1 lan8187/lan8187i system block diagram hubs and switches with multiple integrated macs and external ph ys can have a large pin count due to the high number of pins needed fo r each mii interface. an increa sing pin count causes increasing cost. the rmii interface is intended for use on switch based asics or other embedded solutions requiring minimal pincount for ethernet connectivity. rmii requires only 6 pins for each mac to phy interface plus one common reference clock. the mii requi res 16 pins for each ma c to phy interface. the smsc lan8187/lan8187i is capable of running in rmii mode. please refer to the rmii consortium for more information on the rmii standard http://www.rmii-consort.com . the lan8187/lan8187i referenced throughout this document applies to both the commercial temperature and industrial temperat ure components. the lan8187i refers to only the industrial temperature component. 10/100 media access controller (mac) or soc smsc lan8187/ lan8187i magnetics ethernet system bus leds/gpio 25 mhz (mii) or 50mhz (rmiii) crystal or external clock mii /rmii
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 9 revision 0.6 (02-24-06) datasheet figure 1.2 lan8187/lan8187i architectural overview 10m rx logic 100m rx logic dsp system: clock data recovery equalizer analog-to- digital 100m pll squelch & filters 10m pll receive section central bias hp auto-mdix management control smi rmii / mii logic txp / txn txd[0..3] tx_en tx_er tx_clk rxd[0..3] rx_dv rx_er rx_clk crs col/crs_dv mdc mdio speed100 link activity fduplex led circuitry gpo circuitry mode control gpo0 gpo1 gpo2 nint nreset rxp / rxn 10m tx logic 10m transmitter 100m tx logic 100m transmitter transmit section pll xtal1 xtal2 mode0 mode1 mode2 phy address latches phyad[0..4] auto- negotiation interrupt generator clk_freq mii mdix control amdix_en ch_select
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 10 smsc lan8187/lan8187i datasheet chapter 2 pin configuration 2.1 package pin-out di agram and signal table figure 2.1 package pinout (top view) gpo1/phyad4 gpo0/mii gpo2 mode0 mode1 mode2 vss1 nc test0 col/crs_dv crs nint/tx_er/txd4 txd3 vddio txd2 txd1 txd0 vss5 nc exres1 avss4 avss3 avdd2 reg_en nc vss6 avdd3 nc link/phyad1 activity/phyad2 fduplex/phyad3 xtal2 nc clkin/xtal1 vss3 nrst lan8187/lan8187i 1 16 48 33 32 64 49 test1 nc nc mdio mdc vss4 tx_en tx_clk amdix_en avdd1 rxp rxn vdd33 17 vdd_core vss2 speed100/phyad0 rxd3 rxd2 rxd1 rxd0 ch_select rx_er/rxd4 rx_clk rx_dv avss2 avss1 txp txn
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 11 revision 0.6 (02-24-06) datasheet table 2.1 lan8187/lan8187i 64-pin tqfp pinout pin no. pin name pin no. pin name 1 gpo0/mii 33 rx_dv 2 gpo1/phyad4 34 rx_clk 3 gpo2 35 rx_er/rxd4 4mode036 nc 5 mode1 37 amdix_en 6 mode2 38 tx_clk 7 vss1 39 tx_en 8 nc 40 vss5 9 test0 41 txd0 10 test1 42 txd1 11 nc 43 vddio 12 nc 44 txd2 13 vdd33 45 txd3 14 vdd_core 46 nint/tx_er/txd4 15 vss2 47 col/crs_dv 16 speed100/phyad0 48 crs 17 link/phyad1 49 avss1 18 nc 50 txn 19 activity/phyad2 51 txp 20 fduplex/phyad3 52 avss2 21 nc 53 avdd1 22 xtal2 54 rxn 23 clkin/xtal1 55 rxp 24 vss3 56 nc 25 nrst 57 avdd2 26 mdio 58 avss3 27 mdc 59 exres1 28 vss4 60 avss4 29 rxd3 61 avdd3 30 rxd2 62 vss6 31 rxd1 63 reg_en 32 rxd0 64 nc
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 12 smsc lan8187/lan8187i datasheet chapter 3 pin description this chapter describes the signals on each pin. when a lower case ?n? is used at the beginning of the signal name, it indicates that the signal is active lo w. for example, nrst indicates that the reset signal is active low. 3.1 i/o signals i input. digital lvcmos levels. o output. digital lvcmos levels. i/o input or output. digital lvcmos levels. note: the digital signals are not 5v tolerant. the are variable voltage from +1.6v to +3.6v. ai input. analog levels. ao output. analog levels. table 3.1 mii signals signal name type description txd0 i transmit data 0 : bit 0 of the 4 data bits that are accepted by the phy for transmission. txd1 i transmit data 1 : bit 1 of the 4 data bits that are accepted by the phy for transmission. txd2 i transmit data 2 : bit 2 of the 4 data bits that are accepted by the phy for transmission note: this signal should be grounded in rmii mode. txd3 i transmit data 3 : bit 3 of the 4 data bits that are accepted by the phy for transmission. note: this signal should be grounded in rmii mode nint/ tx_er/ txd4 i/o mii transmit error : when driven high, the 4b/5b encode process substitutes the transmit error code-group (/h/) for the encoded data word. this input is ignored in 10base-t operation. mii transmit data 4: in symbol interface (5b decoding) mode, this signal becomes the mii transmit data 4 line, the msb of the 5-bit symbol code-group. notes: ? this signal is not used in rmii mode. ? this signal is mux?d with nint ? see section 4.10, "(tx_er/txd4)/nint strapping," on page 30 for additional information on configuration/strapping options. tx_en i transmit enable : indicates that valid data is presented on the txd[3:0] signals, for transmission . in rmii mode, only txd[1:0] have valid data. tx_clk o transmit clock : 25mhz in 100base-tx mode. 2.5mhz in 10base-t mode. note: this signal is not used in rmii mode
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 13 revision 0.6 (02-24-06) datasheet rxd0 o receive data 0 : bit 0 of the 4 data bits that are sent by the phy in the receive path. rxd1 o receive data 1 : bit 1 of the 4 data bits that are sent by the phy in the receive path. rxd2 o receive data 2 : bit 2 of the 4 data bits that sent by the phy in the receive path. note: this signal is not used in rmii mode. rxd3/ nintsel o receive data 3 : bit 3 of the 4 data bits that sent by the phy in the receive path. nintsel : on power-up or external reset, the mode of the nint/txer/txd4 pin is selected. ? when floated or pulled to vddio, nint is selected (default). ? when pulled low to vss through a pull-down resistor (see table 4.3, ?boot strapping c onfiguration resistors,? on page 32 ), txer/txd4 is selected. notes: ? rxd3 is not used in rmii mode ? if the nint/txer/txd4 pin is configured for nint mode, it needs a pull-up re sistor to vddio. ? see section 4.10, "(tx_er/txd4)/nint strapping," on page 30 for additional information on configuration/strapping options. rx_er/ rxd4 i/o receive error : asserted to indicate that an error was detected somewhere in the frame presently being transferred from the phy. mii receive data 4 : in symbol interface (5b decoding) mode, this signal is the mii receive data 4 signal, the msb of the received 5-bit symbol code-group. notes: ? the rx_er signal is optional in rmii mode. rx_clk o receive clock : 25mhz in 100base-tx mode. 2.5mhz in 10base-t mode. notes: ? this signal is not used in rmii mode col/crs_dv o mii collision detect : asserted to indicate detection of collision condition. rmii crs_dv (carrier sense/receive data valid) asserted to indicate when the receive medium is non-idle. when a 10bt packet is received, crs_dv is as serted, but rxd[1:0] is held low until the sfd byte (10101011) is received. in 10bt, half- duplex mode, transmitted data is not looped back onto the receive data pins, per the rmii standard. note: see section 4.6.3, "mii vs. rmii configuration," on page 26 for more details. table 3.1 mii signals (continued) signal name type description
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 14 smsc lan8187/lan8187i datasheet table 3.2 led signals signal name type description crs o carrier sense : indicates detection of carrier. rx_dv o receive data valid : indicates that recovered and decoded data nibbles are being presented on rxd[3:0]. note: this signal is not used in rmii mode. speed100/ phyad0 i/o led1 ? speed100 indication. active i ndicates that the selected speed is 100mbps. inactive indicates that the selected speed is 10mbps. note: this signal is mux?d with phyad0 link/ phyad1 i/o led2 ? link on indication. active indicates that the link (100base-tx or 10base-t) is on. note: this signal is mux?d with phyad1 activity/ phyad2 i/o led3 ? activity indication. active indicates that there is carrier sense (crs) from the active pmd. note: this signal is mux?d with phyad2 fduplex/ phyad3 i/o led4 ? duplex indication. active indicates that the phy is in full-duplex mode. note: this signal is mux?d with phyad3 table 3.3 management signals signal name type description mdio i/o management data input/output : serial management data input/output. mdc i management clock : serial management clock. table 3.4 boot strap configuration inputs a signal name type description gpo1/ phyad4 i/o phy address bit 4: set the default address of the phy. this signal is mux?d with gpo1 fduplex/ phyad3 i/o phy address bit 3: set the default address of the phy. note: this signal is mux?d with fduplex activity/ phyad2 i/o phy address bit 2: set the default address of the phy. note: this signal is mux?d with activity link/ phyad1 i/o phy address bit 1: set the default address of the phy. note: this signal is mux?d with link speed100/ phyad0 i/o phy address bit 0: set the default address of the phy. note: this signal is mux?d with speed100
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 15 revision 0.6 (02-24-06) datasheet mode2 i phy operating mode bit 2: set the default mode of the phy. see section 5.4.9.2, "mode bu s ? mode[2:0]," on page 51 , for the mode options. mode1 i phy operating mode bit 1: set the default mode of the phy. see section 5.4.9.2, "mode bu s ? mode[2:0]," on page 51 , for the mode options. mode0 i phy operating mode bit 0: set the default mode of the phy. see section 5.4.9.2, "mode bu s ? mode[2:0]," on page 51 , for the mode options. test1 i test mode select 1: must be left floating. test0 i test mode select 0: must be left floating. reg_en i regulator enable : internal +1.8v regulator enable: vddio ? enables internal regulator. vss? disables internal regulator. amdix_en i hp auto-mdix enable: auto-mdix mode enable. +3.3v ? enables hp auto-mdix. 0v ? disables hp auto-mdix ch_select i channel select: with auto-mdix disabled above, vddio ? enables hp auto-mdix. 0v ? disables hp auto-mdix gpo0/mii i/o general purpose output 0 ? general purpose output signal. driven by bits in registers 27 and 31. mii ? mii/rmii mode selection is latched on the rising edge of the internal reset (nreset) based on the following strapping: float the gpo0 pin for mii mode or pull-high with an external pull-up resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to vddio to set the device in rmii mode. note: see section 4.6.3, "mii vs. rmii configuration," on page 26 for more details. a.on nrst transition high, the phy latches the state of the configuration pins in this table. table 3.5 general signals signal name type description nint i/o lan interrupt ? active low output. place a pull-up external resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to vcc 3.3v. notes: ? this signal is mux?d with tx_er/txd4 ? see section 4.10, "(tx_er/txd4)/nint strapping," on page 30 for additional details on strapping options. nrst i external reset ? input of the system rese t. this signal is active low. table 3.4 boot strap configuration inputs a signal name type description
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 16 smsc lan8187/lan8187i datasheet clkin/xtal1 i clock input ? 25 mhz or 50 mhz external clock or crystal input. in mii mode, this signal is the 25 mhz reference input clock in rmii mode, this signal is the 50 mhz reference input clock which is typically also driven to the rmii compliant ethernet mac clock input. note: see section 4.10, "(tx_er/tx d4)/nint strapping," on page 30 for additional details on strapping options. xtal2 o clock output ? 25 mhz crystal output. note: see section 4.10, "(tx_er/tx d4)/nint strapping," on page 30 for additional details on strapping options. also, float this pin if using an external clock being driven through clkin/xtal1 gpo2 o general purpose output 2 ? general purpose output signal driven by bits in registers 27 and 31. gpo1 o general purpose output 1 ? general purpose output signal driven by bits in registers 27 and 31. this signal is mux?d with phyad4. gpo0/mii i/o general purpose output 0 ? general purpose output signal. driven by bits in registers 27 and 31. mii ? mii/rmii mode selection is latched on the rising edge of the internal reset (nreset) based on the following strapping: float the gpo0 pin for mii mode or pull-high with an external (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) resistor to vddio to set the device in rmii mode. note: see section 4.6.3, "mii vs. rmii configuration," on page 26 for more details. table 3.6 10/100 line interface signal name type description txp ao transmit data : 100base-tx or 10base-t differential transmit outputs to magnetics. txn ao transmit data : 100base-tx or 10base-t differential transmit outputs to magnetics. rxp ai receive data : 100base-tx or 10base-t differential receive inputs from magnetics. rxn ai receive data : 100base-tx or 10base-t differential receive inputs from magnetics. table 3.7 analog references signal name type description exres1 ai connects to reference resistor of value 12.4k-ohm, 1% connected as described in the analog layout guidelines. table 3.5 general signals (continued) signal name type description
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 17 revision 0.6 (02-24-06) datasheet table 3.8 no connect signals signal name type description nc no connect table 3.9 power signals signal name type description avdd1 power +3.3v analog power avdd2 power +3.3v analog power avdd3 power +3.3v analog power avss1 power analog ground avss2 power analog ground avss3 power analog ground avss4 power analog ground vdd_core power +1.8v (core vo ltage) - 1.8v regulator output for digital circuitry on chip. place a 0.1uf capacitor near this pin and connect the capacitor from this pin to ground. in parallel, place a 4.7uf +/- 20% low esr capacitor near this pin and connect the capacitor from this pin to ground. x5r or x7r ceramic capacitors are recommended since they exhibit an esr lower than 0.1ohm at frequencies greater than 10khz. vdd33 power +3.3v digital power vddio power +1.6v to +3.6v vari able i/o pad power vss1 power digital ground (gnd) vss2 power digital ground (gnd) vss3 power digital ground (gnd) vss4 power digital ground (gnd) vss5 power digital ground (gnd) vss6 power digital ground (gnd)
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 18 smsc lan8187/lan8187i datasheet chapter 4 architecture details 4.1 top level functional architecture functionally, the phy can be divided into the following sections: ? 100base-tx transmit and receive ? 10base-t transmit and receive ? mii or rmii interface to the controller ? auto-negotiation to automatically dete rmine the best speed and duplex possible ? management control to read status r egisters and write control registers figure 4.1 100base-tx data path 4.2 100base-tx transmit the data path of the 100base-tx is shown in figure 4.1 . each major block is explained below. 4.2.1 100m transmit da ta across the mii/rmii for mii, the mac controller drives the transmit dat a onto the txd bus and asserts tx_en to indicate valid data. the data is latched by the phy?s mii block on the rising edge of tx_clk. the data is in the form of 4-bit wide 25mhz data. the mac controller drives the transmit data onto the txd bus and asserts tx_en to indicate valid data. the data is latched by the phy?s mii block on the rising edge of ref_clk. the data is in the form of 2-bit wide 50mhz data. 4.2.2 4b/5b encoding the transmit data passes from the mii block to th e 4b/5b encoder. this block encodes the data from 4-bit nibbles to 5-bit symbols (known as ?code-groups?) according to ta b l e 4 . 1 . each 4-bit data-nibble is mapped to 16 of the 32 possible code-groups. the remaining 16 code-groups are either used for control information or are not valid. the first 16 code-groups are referred to by the hexadecimal values of their corresponding data nibbles, 0 through f. the remaining code-groups are given le tter designations with slashes on either side. for example, an idle code-group is /i/, a tr ansmit error code-group is /h/, etc. mac tx driver mlt-3 converter nrzi converter 4b/5b encoder magnetics cat-5 rj45 25mhz by 5 bits nrzi mlt-3 mlt-3 mlt-3 mlt-3 scrambler and piso 125 mbps serial mii 25mhz by 4 bits tx_clk (for mii only) ext ref_clk (for rmii only) 100m pll m ii 25 m hz by 4 bits or rmii 50mhz by 2 bits
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 19 revision 0.6 (02-24-06) datasheet the encoding process may be bypassed by clearing bit 6 of register 31. when the encoding is bypassed the 5 th transmit data bit is equivalent to tx_er. note that encoding can be bypassed only when th e mac interface is configured to operate in mii mode. table 4.1 4b/5b code table code group sym receiver interpretation transmitter interpretation 11110 0 0 0000 data 0 0000 data 01001 1 1 0001 1 0001 10100 2 2 0010 2 0010 10101 3 3 0011 3 0011 01010 4 4 0100 4 0100 01011 5 5 0101 5 0101 01110 6 6 0110 6 0110 01111 7 7 0111 7 0111 10010 8 8 1000 8 1000 10011 9 9 1001 9 1001 10110 a a 1010 a 1010 10111 b b 1011 b 1011 11010 c c 1100 c 1100 11011 d d 1101 d 1101 11100 e e 1110 e 1110 11101 f f 1111 f 1111 11111 i idle sent after /t/r until tx_en 11000 j first nibble of ssd, translated to ?0101? following idle, else rx_er sent for rising tx_en 10001 k second nibble of ssd, translated to ?0101? following j, else rx_er sent for rising tx_en 01101 t first nibble of esd, causes de-assertion of crs if followed by /r/, else assertion of rx_er sent for falling tx_en 00111 r second nibble of esd, causes deassertion of crs if following /t/, else assertion of rx_er sent for falling tx_en 00100 h transmit error symbol sent for rising tx_er 00110 v invalid, rx_er if during rx_dv invalid 11001 v invalid, rx_er if during rx_dv invalid 00000 v invalid, rx_er if during rx_dv invalid 00001 v invalid, rx_er if during rx_dv invalid
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 20 smsc lan8187/lan8187i datasheet 4.2.3 scrambling repeated data patterns (especially the idle code-grou p) can have power spectral densities with large narrow-band peaks. scrambling the data helps eliminate these peaks and spread the signal power more uniformly over the entire channel bandwidth. this uniform spectral density is required by fcc regulations to prevent excessive emi fr om being radiated by the physical wiring. the seed for the scrambler is generated from the phy address, phyad[4:0], ensuring that in multiple- phy applications, such as repeaters or switc hes, each phy will have its own scrambler sequence. the scrambler also performs the parallel in serial out conversion (piso) of the data. 4.2.4 nrzi and mlt3 encoding the scrambler block passes the 5-bit wide parallel data to the nrzi converter where it becomes a serial 125mhz nrzi data stream. the nrzi is encoded to mlt-3. mlt3 is a tri-level code where a change in the logic level represents a code bit ?1? and the logic output remaining at the same level represents a code bit ?0?. 4.2.5 100m transmit driver the mlt3 data is then passed to the analog transmitter, which drives the differential mlt-3 signal, on outputs txp and txn, to the twisted pair media acro ss a 1:1 ratio isolation transformer. the 10base- t and 100base-tx signals pass through the same transformer so that common ?magnetics? can be used for both. the transmit ter drives into the 100 impedance of the cat-5 cable. cable termination and impedance matching require external components. 4.2.6 100m phase lock loop (pll) the 100m pll locks onto reference clock and genera tes the 125mhz clock used to drive the 125 mhz logic and the 100base-tx transmitter. 00010 v invalid, rx_er if during rx_dv invalid 00011 v invalid, rx_er if during rx_dv invalid 00101 v invalid, rx_er if during rx_dv invalid 01000 v invalid, rx_er if during rx_dv invalid 01100 v invalid, rx_er if during rx_dv invalid 10000 v invalid, rx_er if during rx_dv invalid table 4.1 4b/5b code table (continued) code group sym receiver interpretation transmitter interpretation
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 21 revision 0.6 (02-24-06) datasheet figure 4.2 receive data path 4.3 100base-tx receive the receive data path is shown in figure 4.2 . detailed descriptions are given below. 4.3.1 100m receive input the mlt-3 from the cable is fed into the phy (on inputs rxp and rxn) via a 1:1 ratio transformer. the adc samples the incoming differential signal at a rate of 125m samples per second. using a 64- level quanitizer it generates 6 digital bits to repr esent each sample. the dsp adjusts the gain of the adc according to the observed signal levels such t hat the full dynamic range of the adc can be used. 4.3.2 equalizer, baseline wander corr ection and clock and data recovery the 6 bits from the adc are fed into the dsp bl ock. the equalizer in the dsp section compensates for phase and amplitude distortion caused by the ph ysical channel consisting of magnetics, connectors, and cat- 5 cable. the equalizer can restore the signal for any good-quality cat-5 cable between 1m and 150m. if the dc content of the signal is such that the low-frequency comp onents fall below the low frequency pole of the isolation transformer, then the dro op characteristics of t he transformer will become significant and baseline wander (blw) on the receiv ed signal will result. to prevent corruption of the received data, the phy corrects for blw and c an receive the ansi x3.263-1995 fddi tp-pmd defined ?killer packet? with no bit errors. the 100m pll generates multiple phas es of the 125mhz clock. a mult iplexer, controlled by the timing unit of the dsp, selects the optimum phase for sa mpling the data. this is used as the received recovered clock. this clock is used to ex tract the serial data from the received signal. 4.3.3 nrzi and mlt-3 decoding the dsp generates the mlt-3 recovered levels that are fed to the mlt-3 converter. the mlt-3 is then converted to an nrzi data stream. mac a/d converter mlt-3 converter nrzi converter 4b/5b decoder magnetics cat-5 rj45 100m pll mii 25mhz by 4 bits or rmii 50mhz by 2 bits rx_clk (for mii only) 25mhz by 5 bits nrzi mlt-3 mlt-3 mlt-3 6 bit data descrambler and sipo 125 mbps serial dsp: timing recovery, equalizer and blw correction mlt-3 mii/rmii 25mhz by 4 bits ext ref_clk (for rmii only)
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 22 smsc lan8187/lan8187i datasheet 4.3.4 descrambling the descrambler performs an inverse function to t he scrambler in the transmitter and also performs the serial in parallel out (sipo) conversion of the data. during reception of idle (/i/) symbols. the descrambler synchron izes its descrambler key to the incoming stream. once synchronizati on is achieved, the descrambler locks on this key and is able to descramble incoming data. special logic in the descrambler ensures synchronization with the remote phy by searching for idle symbols within a window of 4000 bytes (40us). th is window ensures that a maximum packet size of 1514 bytes, allowed by the ieee 802. 3 standard, can be received with no interference. if no idle- symbols are detected within this time-period, rece ive operation is aborted and the descrambler re-starts the synchronization process. the descrambler can be bypassed by setting bit 0 of register 31. 4.3.5 alignment the de-scrambled signal is then aligned into 5-bit code-groups by recognizing the /j/k/ start-of-stream delimiter (ssd) pair at the start of a packet. once the code-word alignment is determined, it is stored and utilized until the next start of frame. 4.3.6 5b/4b decoding the 5-bit code-groups are translated into 4-bit da ta nibbles according to the 4b/5b table. the translated data is presented on th e rxd[3:0] signal lines. the ssd, /j/k/, is translated to ?0101 0101? as the first 2 nibbles of the mac preamble. reception of the ssd causes the phy to assert the rx_dv signal, indicating that valid data is available on the rxd bus. successive valid code-groups are translated to data nibbles. receptio n of either the end of stream delim iter (esd) consisting of the /t/r/ symbols, or at least two /i/ symbols causes the phy to de-assert carrier sense and rx_dv. these symbols are not translated into data. the decoding process may be bypassed by clearing bit 6 of register 31. when the decoding is bypassed the 5 th receive data bit is driven out on rx_er/rxd4. decoding may be bypassed only when the mac interface is in mii mode. 4.3.7 receive data valid signal the receive data valid signal (rx_dv) indicates that recovered and decoded nibbles are being presented on the rxd[3:0] outputs synchronous to rx_clk. rx_dv becomes active after the /j/k/ delimiter has been recognized and rxd is aligned to nibble boundaries. it remains active until either the /t/r/ delimiter is recognized or link test indicates failure or sigdet becomes false. rx_dv is asserted when the first nibble of trans lated /j/k/ is r eady for transfer over the media independent interface (mii). figure 4.3 relationship between recei ved data and specific mii signals 5d 5 data data data data rxd rx_dv rx_clk 5d 5 data data data data clear-text 5 jk 5 55 tr idle
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 23 revision 0.6 (02-24-06) datasheet 4.3.8 receiver errors during a frame, unexpected code-groups are consid ered receive errors. expected code groups are the data set (0 through f), and the /t/r/ (esd) symbol pair. when a receive error occurs, the rx_er signal is asserted and arbitrary data is driven onto the rxd[3:0] lines. should an error be detected during the time that the /j/k/ delim iter is being decoded (bad ssd error), rx_er is asserted true and the value ?1110? is driven onto the rxd[3:0] lines. note that the valid data signal is not yet asserted when the bad ssd error occurs. 4.3.9 100m receive data across the mii/rmii interface in mii mode, the 4-bit data nibbles are sent to th e mii block. these data nibbles are clocked to the controller at a rate of 25mhz. the controller samples the data on the rising edge of rx_clk. to ensure that the setup and hold requirements are met, the nibbles are clocked out of the phy on the falling edge of rx_clk. rx_clk is the 25mhz output clock fo r the mii bus. it is re covered from the received data to clock the rxd bus. if there is no received signal, it is derived from the system reference clock (clkin). when tracking the received data, rx_clk has a maximum jitter of 0.8ns (provided that the jitter of the input clock, clkin, is below 100ps). in rmii mode, the 2-bit data nibbles are sent to the rmii block. these data nibbles are clocked to the controller at a rate of 50mhz. the controller samples the data on the rising edge of clkin/xtal1 (ref_clk). to ensure that the setup and hold requirements are met, the nibbles are clocked out of the phy on the falling edge of clkin/xtal1 (ref_clk). 4.4 10base-t transmit data to be transmitted comes from the mac layer co ntroller. the 10base-t transmitter receives 4-bit nibbles from the mii at a rate of 2.5mhz and converts them to a 10mbps serial data stream. the data stream is then manchester-encoded and sent to the analog transmitter, which drives a signal onto the twisted pair via the external magnetics. the 10m transmitter uses the following blocks: ? mii (digital) ? tx 10m (digital) ? 10m transmitter (analog) ? 10m pll (analog) 4.4.1 10m transmit data ac ross the mii/rmii interface the mac controller drives the tran smit data onto the txd bus. for mii, when the controller has driven tx_en high to indicate valid data, the data is latched by the mii block on the rising edge of tx_clk. the data is in the form of 4-bit wide 2.5mhz data. in order to comply with legacy 10base-t mac/cont rollers, in half-duplex mode the phy loops back the transmitted data, on the receive path. this d oes not confuse the mac/ controller since the col signal is not asserted during this time. the phy also supports the sqe (heartbeat) signal. see section 5.4.2, "collision detect," on page 49 , for more details. for rmii, txd[1:0] shall transition synchronously with respect to ref_clk. when tx_en is asserted, txd[1:0] are accepted for transmissi on by the lan8187/lan8187i. txd[1: 0] shall be ?00? to indicate idle when tx_en is deasserted. va lues of txd[1:0] othe r than ?00? when tx_en is deasserted are reserved for out-of-band signalling (to be defined). va lues other than ?00? on txd[1:0] while tx_en is deasserted shall be ignored by the lan8187/lan8187i.txd[1:0] shall provide valid data for each ref_clk period while tx_en is asserted.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 24 smsc lan8187/lan8187i datasheet 4.4.2 manchester encoding the 4-bit wide data is sent to the tx10m block. th e nibbles are converted to a 10mbps serial nrzi data stream. the 10m pll locks onto the external cl ock or internal oscillator and produces a 20mhz clock. this is used to manchester encode the nrz data stream. when no data is being transmitted (tx_en is low), the tx10m block outputs normal link pulses (nlps) to maintain communications with the remote link partner. 4.4.3 10m transmit drivers the manchester encoded data is sent to the anal og transmitter where it is shaped and filtered before being driven out as a differential signal across the txp and txn outputs. 4.5 10base-t receive the 10base-t receiver gets the manchester- encoded analog signal from the cable via the magnetics. it recovers the receive clock from the signal and uses this clock to recover the nrzi data stream. this 10m serial data is converted to 4-bit data nibbles which are passed to the controller across the mii at a rate of 2.5mhz. this 10m receiver uses the following blocks: ? filter and squelch (analog) ? 10m pll (analog) ? rx 10m (digital) ? mii (digital) 4.5.1 10m receive input and squelch the manchester signal from the cable is fed into the phy (on inputs rxp and rxn) via 1:1 ratio magnetics. it is first filtered to reduce any out-of-band noise. it then passes through a squelch circuit. the squelch is a set of amplitude and timi ng comparators that norma lly reject differential voltage levels below 300mv and detect and re cognize differential voltages above 585mv. 4.5.2 manchester decoding the output of the squelch goes to the rx10m block where it is validated as manchester encoded data. the polarity of the signal is also checked. if the polarity is reversed (local rxp is connected to rxn of the remote partner and vice versa), then this is identified and corrected. the reversed condition is indicated by the flag ?xpol?, bit 4 in register 27. the 10m pll is locked onto the received manchester signal and from this, generates the received 20mhz clock. using this clock, the manchester encoded data is extracted and conver ted to a 10mhz nrzi dat a stream. it is then converted from serial to 4-bit wide parallel data. the rx10m block also detects valid 10base-t idle signals - normal link pulses (nlps) - to maintain the link. 4.5.3 10m receive data across the mii/rmii interface for mii, the 4 bit data nibbles are sent to the mii block. in mii mode, these data nibbles are valid on the rising edge of the 2.5 mhz rx_clk. for rmii, the 2bit data nibbles are s ent to the rmii block. in rmii mode, these data nibbles are valid on the rising edge of the rmii ref_clk.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 25 revision 0.6 (02-24-06) datasheet 4.5.4 jabber detection jabber is a condition in which a station transmits for a period of time longer than the maximum permissible packet length, usually due to a fault condi tion, that results in ho lding the tx_en input for a long period. special logic is used to detect the jabber state and abort the transmission to the line, within 45ms. once tx_en is deasserted, the logic resets the jabber condition. as shown in ta b l e 5 . 3 1 , bit 1.1 indicates that a jabber condition was detected. 4.6 mac interface the mii/rmii block is responsible fo r the communication with the controller. special sets of hand-shake signals are used to indicate that valid received/tra nsmitted data is present on the 4 bit receive/transmit bus. the device must be configured in mii or rmii mode. this is done by specific pin strapping configurations. see section section 4.6.3, "mii vs. rm ii configuration," on page 26 for information on pin strapping and how the pins are mapped differently. 4.6.1 mii the mii includes 16 interface signals: ? transmit data - txd[3:0] ? transmit strobe - tx_en ? transmit clock - tx_clk ? transmit error - tx_er/txd4 ? receive data - rxd[3:0] ? receive strobe - rx_dv ? receive clock - rx_clk ? receive error - rx_er/rxd4 ? collision indication - col ? carrier sense - crs in mii mode, on the transmit path, the phy drives the transmit clock, tx_clk , to the controller. the controller synchronizes the transmit data to the rising edge of tx_clk. the controller drives tx_en high to indicate valid transmit data. the controller drives tx_er high when a transmit error is detected. on the receive path, the phy drives both the re ceive data, rxd[3:0], and the rx_clk signal. the controller clocks in the receive data on the risi ng edge of rx_clk when the phy drives rx_dv high. the phy drives rx_er high when a receive error is detected. 4.6.2 rmii the smsc lan8187/lan8187i supports the low pi n count reduced media independent interface (rmii) intended for use between ethernet phys and switch asics. under ieee 802.3, an mii comprised of 16 pins for data and control is defin ed. in devices incorporating many macs or phy interfaces such as switches, the number of pins can add significant cost as the port counts increase. the management interface (mdio/mdc) is identica l to mii. the rmii interface has the following characteristics: ? it is capable of supporting 10mb/s and 100mb/s data rates ? a single clock reference is sourced from th e mac to phy (or from an external source) ? it provides independent 2 bit wide (di-bit) transmit and receive data paths
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 26 smsc lan8187/lan8187i datasheet ? it uses lvcmos signal levels, compatib le with common digital cmos asic processes the rmii includes 6 interface signals with one of the signals being optional: ? transmit data - txd[1:0] ? transmit strobe - tx_en ? receive data - rxd[1:0] ? receive error - rx_er (optional) ? carrier sense - crs_dv ? reference clock - clkin/xtal1 (rmii referenc es usually define this signal as ref_clk) 4.6.2.1 reference clock the reference clock - clkin, is a continuous clock that provides the timing reference for crs_dv, rxd[1:0], tx_en, txd[1:0], and rx_er. the refere nce clock is sourced by the mac or an external source. switch implementations may choose to provide ref_clk as an in put or an output depending on whether they provide a ref_clk output or re ly on an external clock distribution device. the ?reference clock? frequency must be 50 mhz +/- 50 ppm with a duty cycle between 35% and 65% inclusive. the smsc lan8187/lan8187i uses the ?reference clock? as the network clock such that no buffering is required on the transmit data path. the smsc lan8187/lan8187i will recover the clock from the incoming data stream, the receiver will account for differences between the local ref_clk and the recovered clock through use of sufficient elasticity buffering. the elasticity buffer does not affect the inter-packet gap (ipg) for received ip gs of 36 bits or greater. to tolerate the clock variations specified here for ethernet mtus, the elasti city buffer shall tolerate a minimum of +/-10 bits. 4.6.2.2 crs_dv - carrier sense/receive data valid the crs_dv is asserted by the lan8187/lan81 87i when the receive medium is non-idle. crs_dv is asserted asynchronously on detection of carrier d ue to the criteria releva nt to the operating mode. that is, in 10base-t mode, when squelch is pa ssed or in 100base-x mode when 2 non-contiguous zeroes in 10 bits are detected, carrier is said to be detected. loss of carrier shall result in the deassertion of crs_dv synchronous to the cycle of ref_clk which presents the first di-bit of a nibble onto rxd[1:0] (i.e. crs_dv is deasserted only on nibble boundaries). if the lan8187/lan8187i has additional bits to be presented on rxd[1:0] following the initial deassertion of crs_dv, then the lan8187/lan8187i shall assert crs_dv on cycles of ref_clk which present the second di-bit of each nibble and de-assert crs_dv on cycles of ref_clk which present the first di -bit of a nibble. the result is: starting on nibble boundaries crs_dv toggles at 25 mhz in 100mb/s mode and 2.5 mhz in 10mb/s mode when crs ends before rx_dv (i.e. the fifo still has bits to transfer wh en the carrier event ends.) therefore, the mac can accurately recover rx_dv and crs. during a false carrier event, crs_dv shall remain asserted for the duration of carrier activity. the data on rxd[1:0] is considered valid once crs_dv is as serted. however, since the assertion of crs_dv is asynchronous relative to ref_clk, the data on rxd[1:0] shall be ?00? until proper receive signal decoding takes place. 4.6.3 mii vs. rmii configuration the lan8187/lan8187i must be configured to support the mii or rmii bus for connectivity to the mac. this configuration is done through the gpo0/mii pin. mii or rmii mode selection is latched on the rising edge of the internal reset (nreset) based on the strapping of the gpo0/mii pin. to select mii mode, float the gpo0/mii pin. to select rmii mode, pull- high with an external resistor (see table 4.3, ?boot strapping config uration resistors,? on page 32 ) to vdd33.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 27 revision 0.6 (02-24-06) datasheet most of the mii and rmii pins are multiplexed. table 4.2, "mii/rmii signal mapping" , shown below, describes the relationship of the related device pi ns to what pins are used in mii and rmii mode. note 4.1 in rmii mode, this pin needs to tied to vss. note 4.2 the rx_er signal is optional on the rmii bus. this signal is required by the phy, but it is optional for the mac. the mac can choose to ignore or not use this signal. 4.7 auto-negotiation the purpose of the auto-negotiation function is to automatically configure the phy to the optimum link parameters based on the capabilities of its li nk partner. auto-negotiation is a mechanism for exchanging configuration information between two lin k-partners and automatically selecting the highest performance mode of operation supported by both si des. auto-negotiation is fully defined in clause 28 of the ieee 802.3 specification. once auto-negotiation has completed, information ab out the resolved link can be passed back to the controller via the serial management interface (smi). the results of the negotiation process are reflected in the speed indication bits in register 31, as well as the link partner ability register (register 5). the auto-negotiation protocol is a purely physical layer activity and proceeds independently of the mac controller. table 4.2 mii/rmii signal mapping signal name mii mode rmii mode txd0 txd0 txd0 txd1 txd1 txd1 tx_en tx_en tx_en rx_er/ rxd4 rx_er/ rxd4/ rx_er note 4.2 col/crs_dv col crs_dv rxd0 rxd0 rxd0 rxd1 rxd1 rxd1 txd2 txd2 note 4.1 txd3 txd3 note 4.1 tx_er/ txd4 tx_er/ txd4 crs crs rx_dv rx_dv rxd2 rxd2 rxd3 rxd3 tx_clk tx_clk rx_clk rx_clk clkin/xtal1 clkin/xtal1 ref_clk
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 28 smsc lan8187/lan8187i datasheet the advertised capabilities of the phy are stored in register 4 of the sm i registers. the default advertised by the phy is determined by user-defined on-chip signal options. the following blocks are activated during an auto-negotiation session: ? auto-negotiation (digital) ? 100m adc (analog) ? 100m pll (analog) ? 100m equalizer/blw/clock recovery (dsp) ? 10m squelch (analog) ? 10m pll (analog) ? 10m transmitter (analog) when enabled, auto-negotiation is started by t he occurrence of one of the following events: ? hardware reset ? software reset ? power-down reset ? link status down ? setting register 0, bit 9 high (auto-negotiation restart) on detection of one of these event s, the phy begins auto-negotiation by transmitting bursts of fast link pulses (flp). these are bur sts of link pulses from the 10m transmitter. they are shaped as normal link pulses and can pass uncorrupted down cat-3 or cat-5 cable. a fast link pulse burst consists of up to 33 pulses. the 17 odd-number ed pulses, which are always present, frame the flp burst. the 16 even-numbered pulses, which may be present or absent, cont ain the data word being transmitted. presence of a data pulse repres ents a ?1?, while absence represents a ?0?. the data transmitted by an flp burst is known as a ?link code word.? these are defined fully in ieee 802.3 clause 28. in summary, the phy advertises 8 02.3 compliance in its selector field (the first 5 bits of the link code word). it advertises its technology abi lity according to the bits set in register 4 of the smi registers. there are 4 possible matches of the technology ab ilities. in the order of priority these are: ? 100m full duplex (highest priority) ? 100m half duplex ? 10m full duplex ? 10m half duplex if the full capabilities of the phy are advertised (1 00m, full duplex), and if the link partner is capable of 10m and 100m, then auto-negotiation selects 1 00m as the highest performance mode. if the link partner is capable of half and full duplex modes, then auto-negotiation selects full duplex as the highest performance operation. once a capability match has been determined, the link code words are repeated with the acknowledge bit set. any difference in the main content of the link code words at this time will cause auto-negotiation to re-start. auto-negotiation will also re-start if not all of the required flp bursts are received. the capabilities advertised during auto-negotiation by the phy are initially determined by the logic levels latched on the mode[2:0] bus after reset completes. this bus can also be used to disable auto- negotiation on power-up. writing register 4 bits [8:5] allows software control of the capabilities advertised by the phy. writing register 4 does not automatically re -start auto-negotiation. register 0, bit 9 must be set before the new abilities will be advertised. auto-negotiation can also be disabled via software by clearing register 0, bit 12. the lan8187/lan8187i does not support ?next page? capability.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 29 revision 0.6 (02-24-06) datasheet 4.7.1 parallel detection if the lan8187/lan8187i is connected to a device lacking the ability to auto-negotiate (i.e. no flps are detected), it is able to determine the speed of the link based on either 100m mlt-3 symbols or 10m normal link pulses. in this case the link is presumed to be half duplex per the ieee standard. this ability is known as ?parallel detection.? th is feature ensures interoperability with legacy link partners. if a link is formed via para llel detection, then bit 0 in register 6 is cleared to indicate that the link partner is not capable of auto-negotiation. the controller has access to this information via the management interface. if a fault occurs during pa rallel detection, bit 4 of register 6 is set. register 5 is used to store the link partner abilit y information, which is coded in the received flps. if the link partner is not auto-negotiation capable, then register 5 is updated after completion of parallel detection to reflect the speed capability of the link partner. 4.7.2 re-starting auto-negotiation auto-negotiation can be re-started at any time by sett ing register 0, bit 9. auto-negotiation will also re- start if the link is broken at any time. a broken link is caused by signal loss. this may occur because of a cable break, or because of an interruption in the signal transmitted by the link partner. auto- negotiation resumes in an attempt to determine the new link configuration. if the management entity re-starts au to-negotiation by writing to bi t 9 of the control register, the lan8187/lan8187i will respond by stopping all transmission/receiving operations. once the break_link_timer is done, in the auto-negotiation state-machine (approximately 1200ms) the auto- negotiation will re-start. the link partner will have also dropped the link due to lack of a received signal, so it too will resume auto-negotiation. 4.7.3 disabling auto-negotiation auto-negotiation can be disabled by setting regist er 0, bit 12 to zero. the device will then force its speed of operation to reflect the information in regist er 0, bit 13 (speed) and register 0, bit 8 (duplex). the speed and duplex bits in register 0 should be ignored when auto-negotiation is enabled. 4.7.4 half vs. full duplex half duplex operation relies on the csma/cd (car rier sense multiple access / collision detect) protocol to handle network traffic and collisions. in this mode, the carrier sense signal, crs, responds to both transmit and receive activity. in this mode, if data is received while the phy is transmitting, a collision results. in full duplex mode, the phy is able to transmit and receive data simultaneously. in this mode, crs responds only to receive activity. the csma/cd pr otocol does not apply and collision detection is disabled. 4.8 hp auto-mdix hp auto-mdix facilitates the use of cat-3 (10 base -t) or cat-5 (100 base-t ) media utp interconnect cable without consideration of inte rface wiring scheme. if a user plugs in either a direct connect lan cable, or a cross-over patch cable, as shown in figure 4.4 on page 30 , the smsc lan8187/lan8187i auto-mdix phy is capable of configuring the tx p/txn and rxp/rxn pins for correct transceiver operation. the internal logic of the device detects the tx and rx pins of the connecting device. since the rx and tx line pairs are interchangeable, special pcb design considerations are needed to accommodate the symmetrical magnetics and termination of an auto-mdix design. the auto-mdix function can be disabled through an inte rnal register 27.15, or the external control pins amdix_en. when disabled the tx and rx pins can be configured with the channel select (ch_select) pin as desired.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 30 smsc lan8187/lan8187i datasheet 4.9 internal +1.8v regulator disable part of the lan8187/ lan8187i smsc flexpwr tm technology is the ability to disable the internal +1.8v regulator. this further increases the power savings as a more efficient external switching regulator can provide the necessary +1.8v to the internal phy circuitry. 4.9.1 disable the internal +1.8v regulator to disable the +1.8v internal regulator, a pulldown strapping resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) is attached from reg_en to vddio. when a reset event occurs, the phy will sample the reg_en pin to determine if the internal regulator should turn on. if the pin is grounded to vss, then the internal regulator is off, and the system needs to supply +1.8v +/- 10% to the vdd_core pin. a 4.7uf low esr and 0.1uf capacitor must be added to vdd_core and placed close to the phy. this capacitance provides decoupling of the exter nal power supply noise and ensures stability of the internal regulator. 4.9.2 enable the internal +1.8v regulator to enable the internal regulator, a pull-up resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to vddio needs to be added to the reg_en pin. a 4.7uf low esr and 0.1uf capacitor must be added to vdd_core and placed close to the phy. this capacitance provides decoupling of the exter nal power supply noise and ensures stability of the internal regulator. note: for vddio operation below +2.5v, smsc recommends designs add external strapping resistors in addition the internal strapping resistors to ensure proper strapped operation. 4.10 (tx_er/txd4)/nint strapping the tx_er, txd4 and nint functions share a comm on pin. there are two functional modes for this pin, the tx_er/txd4 mode and nint (interrupt) mode. the rxd3 pin is used to select one of these two functional modes. figure 4.4 direct cable connection vs. cross-over cable connection.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 31 revision 0.6 (02-24-06) datasheet the rxd3 pin is latched on the rising edge of the in ternal reset (nreset) to select the mode. the system designer must float the rxd3 pin for nint mode or pull-low with an external resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to vss to set the device in tx_er/txd4 mode. the default setting is high (nint mode). note: for vddio operation below +2.5v, smsc recommends designs add external strapping resistors in addition the internal strapping resistors to ensure proper strapped operation. 4.11 phy address strapping and led output polarity selection the phy address bits are latched on the rising edge of the internal reset (nreset). the 5-bit address word[0:4] is input on the led1, led2, led3, led4, gpo1 output pins. the default setting is all high 5'b1_1111. the address lines are strapped as defined in the diagram below. the led outputs will automatically change polarity based on the presen ce of an external pull-down resi stor. if the led pin is pulled high (by an internal 100k pull-up resistor) to select a logical high phy address, then the led output will be active low. if the led pin is pulled low (by an external pull-down resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to select a logical low phy address, the led output will then be an active high output. to set the phy address on the led pins without leds or on the gpo1 or crs pin, float the pin to set the address high or pull-down the pin with an external resistor (see table 4.3, ?boot strapping configuration resistors,? on page 32 ) to gnd to set the address low. see the figure below: figure 4.5 phy address strapping on led?s 4.12 variable voltage i/o the digital i/o pins on the lan8187/lan8187i are variable voltage to take advantage of low power savings from shrinking technologies. these pins can operate from a low i/o voltage of +1.6v up to +3.6v. due to this low voltage feature addition, the system designer needs to take consideration as for two aspects of their design. boot str apping configuration and i/o voltage stability. led1-led4 ~270 ohms phy address = 0 led output = active high ~10k ohms ~270 ohms led1-led4 vdd phy address = 1 led output = active low
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 32 smsc lan8187/lan8187i datasheet 4.12.1 boot strappi ng configuration. due to a lower i/o voltage, a lower strapping resistor needs to be used to ensure the strapped configuration is latched into th e phy device at power-on reset. note: for vddio operation below +2.5v, smsc recommends designs add external strapping resistors in addition the internal strapping resistors to ensure proper strapped operation. 4.12.2 i/o voltage stability the i/o voltage the system designer applies on vddi o needs to maintain its value with a tolerance of +/- 10%. varying the voltage up or down, afte r the phy has completed power-on reset can cause errors in the phy operation. 4.13 phy management control the management control module includes 3 blocks: ? serial management interface (smi) ? management registers set ? interrupt 4.13.1 serial management interface (smi) the serial management interface is used to contro l the lan8187/lan8187i and obtain its status. this interface supports registers 0 through 6 as require d by clause 22 of the 802.3 standard, as well as ?vendor-specific? registers 16 to 31 allowed by the specification. non-supported registers (7 to 15) will be read as hexadecimal ?ffff?. at the system level there are 2 si gnals, mdio and mdc where mdio is bi-directional open-drain and mdc is the clock. a special feature (enabled by register 17 bit 3) forces the phy to disregard the phy-address in the smi packet causing the phy to respond to any address. this feature is useful in multi-phy applications and in production testing, where the same register can be written in all the phys using a single write transaction. the mdc signal is an aperiodic clock provided by the station management controller (smc). the mdio signal receives serial data (commands) from the contro ller smc, and sends serial data (status) to the smc. the minimum time between edges of the mdc is 160 ns. there is no maximum time between edges. the minimum cycle time (time between two consecutive rising or two consecutive falling edges) is 400 ns. these modest timing requirements allow this inte rface to be easily driven by the i/o port of a microcontroller. the data on the mdio line is latched on the rising edge of the mdc. the frame structure and timing of the data is shown in figure 4.6 and figure 4.7 . table 4.3 boot strapping configuration resistors i/o voltage pull-up/pull-down resistor 3.0 to 3.6 10k ohm resistor 2.0 to 3.0 7.5k ohm resistor 1.6 to 2.0 5k ohm resistor
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 33 revision 0.6 (02-24-06) datasheet the timing relationships of the mdio signals are further described in section 6.1, "serial management interface (smi) timing," on page 53 . figure 4.6 mdio timing and frame structure - read cycle figure 4.7 mdio timing and frame structure - write cycle mdc mdi0 read cycle ... 32 1's 0 1 1 0 a4 a3 a2 a1 a0 r4 r3 r2 r1 r0 d1 ... d15 d14 d0 preamble start of frame op code phy address register address turn around data data from phy data to phy mdc mdio ... 32 1's 0 1 1 0 a4a3a2a1a0r4r3r2r1r0 write cycle d15 d14 d1 d0 ... data preamble start of frame op code phy address register address turn around data to phy
smsc lan8187/lan8187i 34 revision 0.6 (02-24-06) datasheet chapter 5 registers table 5.1 control regist er: register 0 (basic) 15 14 13 12 11 10 9 8 7 6543210 rese t loopbac k speed select a/n enable power down isolat e restart a/n duplex mode collision te s t reserved table 5.2 status register: register 1 (basic) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 100bas e-t4 100base- tx full duplex 100base- tx half duplex 10base- t full duplex 10base- t half duplex reserved a/n complet e remot e fault a/n abilit y link statu s jabbe r detect extende d capabilit y table 5.3 phy id 1 register: register 2 (extended) 1514131211109876543210 phy id number (bits 3-18 of the organizationally unique identifier - oui) table 5.4 phy id 2 register: register 3 (extended) 1514131211109876543210 phy id number (bits 19-24 of the organizationally unique identifier - oui) manufacturer model number manufacturer revision number
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 35 smsc lan8187/lan8187i datasheet note: next page capability is not supported . table 5.5 auto-negotiation advertisement: register 4 (extended) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 next page reserve d remot e fault reserve d symmetric pause operation asymmetri c pause operation 100base- t4 100base- tx full duplex 100base- tx 10base- t full duplex 10base- t ieee 802.3 selector field table 5.6 auto-negotiation link partner base page ability register: register 5 (extended) 15 14 13 121110 9 8 7 6 5 43210 next page acknowled ge remot e fault reserved paus e 100base- t4 100base-tx full duplex 100base- tx 10base-t full duplex 10base- t ieee 802.3 selector field table 5.7 auto-negotiation expansi on register: register 6 (extended) 15141312111098765 4 3 2 1 0 reserved parallel detect fault link partner next page able next page able page received link partner a/n able table 5.8 auto-negotiation link partner next page transmit register: register 7 (extended) 1514131211109876543210 reserved
smsc lan8187/lan8187i 36 revision 0.6 (02-24-06) datasheet table 5.9 register 8 (extended) 1514131211109876543210 ieee reserved table 5.10 register 9 (extended) 1514131211109876543210 ieee reserved table 5.11 register 10 (extended) 1514131211109876543210 ieee reserved table 5.12 register 11 (extended) 1514131211109876543210 ieee reserved table 5.13 register 12 (extended) 1514131211109876543210 ieee reserved table 5.14 register 13 (extended) 1514131211109876543210 ieee reserved
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 37 smsc lan8187/lan8187i datasheet table 5.15 register 14 (extended) 1514131211109876543210 ieee reserved table 5.16 register 15 (extended) 1514131211109876543210 ieee reserved table 5.17 silicon revision register 16: vendor-specific 1514131211109876543210 reserved silicon revision reserved table 5.18 mode control/ status register 17: vendor-specific 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 reserved fastrip edpwrdown reserved lowsqen mdprebp farloopback fastest reserved refclken phyadbp force good link status energyon reserved table 5.19 special modes register 18: vendor-specific 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 miimode clkselfreq dspbp sqbp reserved pllbp adcbp mode phyad
smsc lan8187/lan8187i 38 revision 0.6 (02-24-06) datasheet table 5.20 reserved register 19: vendor-specific 1514131211109876543210 reserved table 5.21 register 24: vendor-specific 1514131211109876543210 reserved table 5.22 register 25: vendor-specific 1514131211109876543210 reserved table 5.23 register 26: vendor-specific 1514131211109876543210 reserved table 5.24 special control/status indications register 27: vendor-specific 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 reserved swrst_fa st sqeof f vcooff_l p reserve d reserve d reserve d reserve d reserve d xpo l autonegs
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 39 smsc lan8187/lan8187i datasheet table 5.25 special internal testability control register 28: vendor-specific 1514131211109876543210 reserved table 5.26 interrupt source flags register 29: vendor-specific 151413121110987654321 0 reserved int7 int6 int5 int4 int3 int2 int1 reserved table 5.27 interrupt mask register 30: vendor-specific 15 14 131211109876543210 amdixctr l reserve d ch_selec t reserved mask bits table 5.28 phy special control/status register 31: vendor-specific 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 reserved reserved special autodone reserved gpo2 gpo1 gpo0 enable 4b5b reserved speed indication reserved scramble disable
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 40 smsc lan8187/lan8187i datasheet 5.1 smi register mapping the following registers are supported (register numbers are in decimal): 5.2 smi register format the mode key is as follows: ? rw = read/write, ? sc = self clearing, ? wo = write only, ? ro = read only, ? lh = latch high, clear on read of register, ? ll = latch low, clear on read of register, ? nasr = not affected by software reset table 5.29 smi register mapping register # description group 0 basic control register basic 1 basic status register basic 2 phy identifier 1 extended 3 phy identifier 2 extended 4 auto-negotiation advertisement register extended 5 auto-negotiation link pa rtner ability register extended 6 auto-negotiation expansion register extended 16 silicon revision register vendor-specific 17 mode control/status register vendor-specific 18 special modes vendor-specific 20 reserved vendor-specific 21 reserved vendor-specific 22 reserved vendor-specific 23 reserved vendor-specific 27 control / status indication register vendor-specific 28 special internal testability controls vendor-specific 29 interrupt source register vendor-specific 30 interrupt mask register vendor-specific 31 phy special control/status register vendor-specific
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 41 revision 0.6 (02-24-06) datasheet table 5.30 register 0 - basic control address name description mode default 0.15 reset 1 = software reset. bit is self-clearing. for best results, when setting this bit do not set other bits in this register. rw/ sc 0 0.14 loopback 1 = loopback mode, 0 = normal operation rw 0 0.13 speed select 1 = 100mbps, 0 = 10mbps. ignored if auto negotiation is enabled (0.12 = 1). rw set by mode[2:0] bus 0.12 auto- negotiation enable 1 = enable auto-negotiate process (overrides 0.13 and 0.8) 0 = disable auto-negotiate process rw set by mode[2:0] bus 0.11 power down 1 = general power down mode, 0 = normal operation rw 0 0.10 isolate 1 = electrical isolation of phy from mii 0 = normal operation rw set by mode[2:0] bus 0.9 restart auto- negotiate 1 = restart auto-negotiate process 0 = normal operation. bit is self-clearing. rw/ sc 0 0.8 duplex mode 1 = full duplex, 0 = half duplex. ignored if auto negotiation is enabled (0.12 = 1). rw set by mode[2:0] bus 0.7 collision test 1 = enable col test, 0 = disable col test rw 0 0.6:0 reserved ro 0 table 5.31 register 1 - basic status address name description mode default 1.15 100base-t4 1 = t4 able, 0 = no t4 ability ro 0 1.14 100base-tx full duplex 1 = tx with full duplex, 0 = no tx full duplex ability ro 1 1.13 100base-tx half duplex 1 = tx with half duplex, 0 = no tx half duplex ability ro 1 1.12 10base-t full duplex 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability ro 1 1.11 10base-t half duplex 1 = 10mbps with half duplex 0 = no 10mbps with half duplex ability ro 1 1.10:6 reserved 1.5 auto-negotiate complete 1 = auto-negotiate process completed 0 = auto-negotiate process not completed ro 0 1.4 remote fault 1 = remote fault condition detected 0 = no remote fault ro/ lh 0
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 42 smsc lan8187/lan8187i datasheet 1.3 auto-negotiate ability 1 = able to perform auto-negotiation function 0 = unable to perform auto-negotiation function ro 1 1.2 link status 1 = link is up, 0 = link is down ro/ ll 0 1.1 jabber detect 1 = jabber condition detected 0 = no jabber condition detected ro/ lh 0 1.0 extended capabilities 1 = supports extended capabilities registers 0 = does not support extended capabilities registers ro 1 table 5.32 register 2 - phy identifier 1 address name description mode default 2.15:0 phy id number assigned to the 3rd through 18th bits of the organizationally unique identifier (oui), respectively. oui=00800fh rw 0007h table 5.33 register 3 - phy identifier 2 address name description mode default 3.15:10 phy id number assigned to the 19 th through 24 th bits of the oui. rw 30h 3.9:4 model number six-bit manufacturer?s model number. rw 0bh 3.3:0 revision number four-bit manufacturer?s revision number. rw 1h table 5.34 register 4 - auto negotiation advertisement address name description mode default 4.15 next page 1 = next page capable, 0 = no next page ability this phy does not support next page ability. ro 0 4.14 reserved ro 0 4.13 remote fault 1 = remote fault detected, 0 = no remote fault rw 0 4.12 reserved 4.11:10 pause operation 00 = no pause 01 = asymmetric pause toward link partner 10 = symmetric pause 11 = both symmetric pause and asymmetric pause toward local device r/w 00 4.9 100base-t4 1 = t4 able, 0 = no t4 ability this phy does not support 100base-t4. ro 0 table 5.31 register 1 - basic status (continued) address name description mode default
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 43 revision 0.6 (02-24-06) datasheet 4.8 100base-tx full duplex 1 = tx with full duplex, 0 = no tx full duplex ability rw set by mode[2:0] bus 4.7 100base-tx 1 = tx able, 0 = no tx ability rw 1 4.6 10base-t full duplex 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability rw set by mode[2:0] bus 4.5 10base-t 1 = 10mbps able, 0 = no 10mbps ability rw set by mode[2:0] bus 4.4:0 selector field [000 01] = ieee 802.3 rw 00001 table 5.35 register 5 - auto negotiation link partner ability address name description mode default 5.15 next page 1 = ?next page? capable, 0 = no ?next page? ability this phy does not support next page ability. ro 0 5.14 acknowledge 1 = link code word received from partner 0 = link code word not yet received ro 0 5.13 remote fault 1 = remote fault detected, 0 = no remote fault ro 0 5.12:11 reserved ro 0 5.10 pause operation 1 = pause operation is supported by remote mac, 0 = pause operation is not supported by remote mac ro 0 5.9 100base-t4 1 = t4 able, 0 = no t4 ability. this phy does not support t4 ability. ro 0 5.8 100base-tx full duplex 1 = tx with full duplex, 0 = no tx full duplex ability ro 0 5.7 100base-tx 1 = tx able, 0 = no tx ability ro 0 5.6 10base-t full duplex 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability ro 0 5.5 10base-t 1 = 10mbps able, 0 = no 10mbps ability ro 0 5.4:0 selector field [00001] = ieee 802.3 ro 00001 table 5.34 register 4 - auto negotiation advertisement (continued) address name description mode default
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 44 smsc lan8187/lan8187i datasheet table 5.36 register 6 - auto negotiation expansion address name descript ion mode default 6.15:5 reserved ro 0 6.4 parallel detection fault 1 = fault detected by parallel detection logic 0 = no fault detected by parallel detection logic ro/ lh 0 6.3 link partner next page able 1 = link partner has next page ability 0 = link partner does not have next page ability ro 0 6.2 next page able 1 = local device has next page ability 0 = local device does not have next page ability ro 0 6.1 page received 1 = new page received 0 = new page not yet received ro/ lh 0 6.0 link partner auto- negotiation able 1 = link partner has auto-negotiation ability 0 = link partner does not have auto-negotiation ability ro 0 table 5.37 register 16 - silicon revision address name description mode default 16.15:10 reserved ro 0 16.9:6 silicon revision four-bit silicon revision identifier. ro 0001 16.5:0 reserved ro 0 table 5.38 register 17 - mode control/status address name description mode default 17.15 reserved write as 0; ignore on read. rw 0 17.14 fastrip 10base-t fast mode: 0 = normal operation 1 = reserved must be left at 0 rw, nasr 0 17.13 edpwrdown enable the energy detect power-down mode: 0 = energy detect power-down is disabled 1 = energy detect power-down is enabled rw 0 17.12 reserved write as 0, ignore on read rw 0 17.11 lowsqen the low_squelch signal is equal to lowsqen and edpwrdown. low_squelch = 1 implies a lower threshold (more sensitive). low_squelch = 0 implies a higher threshold (less sensitive). rw 0 17.10 mdprebp management data preamble bypass: 0 ? detect smi packets with preamble 1 ? detect smi packets without preamble rw 0
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 45 revision 0.6 (02-24-06) datasheet 17.9 farloopback force the module to the far loop back mode, i.e. all the received packets are sent back simultaneously (in 100base-tx only). this bit is only active in rmii mode. in this mode the user needs to supply a 50mhz clock to the phy. this mode works even if mii isolate (0.10) is set. rw 0 17.8 fastest auto-negotiation test mode 0 = normal operation 1 = activates test mode rw 0 17.7:5 reserved write as 0, ignore on read. 17.4 refclken 1= enables special filtering using a 50 mhz clock in 10base-t mode. rw 0 17.3 phyadbp 1 = phy disregards phy address in smi access write. rw 0 17.2 force good link status 0 = normal operation; 1 = force 100tx- link active; note: this bit should be set only during lab testing rw 0 17.1 energyon energyon ? indicates whether energy is detected on the line (see section 5.4.5.2, "energy detect power-down," on page 50 ); it goes to ?0? if no valid energy is detected within 256ms. reset to ?1? by hardware reset, unaffected by sw reset. ro 1 17.0 reserved write as ?0?. ignore on read. rw 0 table 5.39 register 18 - special modes address name description mode default 18.15:14 miimode mii mode : set the mode of the mii: 0 ? mii interface. 1 ? rmii interface rw, nasr 18.13 clkselfreq clock in selected frequency. set the reques ted input clock frequency. this bit drives signal that goes to external logic of the phy and select the desired frequency of the input clock: 0 ? the clock frequency is 25mhz 1 ? reserved ro, nasr 18.12 dspbp dsp bypass mode. used on ly in special lab tests. rw, nasr 0 18.11 sqbp squelch bypass mode. rw, nasr 0 18.10 reserved rw, nasr 18.9 pllbp pll bypass mode. rw, nasr 18.8 adcbp adc bypass mode. rw, nasr table 5.38 register 17 - mode control/status (continued) address name description mode default
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 46 smsc lan8187/lan8187i datasheet 18.7:5 mode phy mode of operation. refer to section 5.4.9.2, "mode bus ? mode[2:0]," on page 51 for more details. rw, nasr 18.4:0 phyad phy address. the phy address is used for the smi address and for the initialization of the cipher (scrambler) key. refer to section 5.4.9.1, "physical address bus - phyad[4:0]," on page 51 for more details. rw, nasr phyad table 5.40 register 27 - special control/status indications address name description mode default 27.15 amdixctrl hp auto-mdix control 0 - auto-mdix enable 1 - auto-mdix disabled (use 27.13 to control channel) rw 0 27.14 reserved reserved rw 0 27.13 ch_select manual channel select 0 - mdi -tx transmits rx receives 1 - mdix -tx receives rx transmits rw 0 27.12 swrst_fast 1 = accelerates sw re set counter from 256 ms to 10 us for production testing. rw 0 27:11 sqeoff disable the sqe test (heartbeat): 0 - sqe test is enabled. 1 - sqe test is disabled. rw, nasr 0 27:10 vcooff_lp forces the receive pll 10m to lock on the reference clock at all times: 0 - receive pll 10m can lock on reference or line as needed (normal operation) 1 - receive pll 10m is locked on the reference clock. in this mode 10m data packets cannot be received. rw, nasr 0 27.9 reserved write as 0. ignore on read. rw 0 27.8 reserved write as 0. ignore on read. rw 0 27.7 reserved write as 0. ignore on read rw 0 27.6 reserved write as 0. ignore on read. rw 0 27.5 reserved write as 0. ignore on read. rw 27.4 xpol polarity state of the 10base-t: 0 - normal polarity 1 - reversed polarity ro 0 27.3:0 autonegs auto-negotiation ?arb? state-machine state ro 1011b table 5.41 register 28 - special internal testability controls address name description mode default 28.15:0 reserved do not write to this register. ignore on read. rw n/a table 5.39 register 18 - special modes (continued) address name description mode default
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 47 revision 0.6 (02-24-06) datasheet table 5.42 register 29 - interrupt source flags address name description mode default 29.15:8 reserved ignore on read. ro/ lh 0 29.7 int7 1 = energyon generated 0 = not source of interrupt ro/ lh 0 29.6 int6 1 = auto-negotiation complete 0 = not source of interrupt ro/ lh 0 29.5 int5 1 = remote fault detected 0 = not source of interrupt ro/ lh 0 29.4 int4 1 = link down (link status negated) 0 = not source of interrupt ro/ lh 0 29.3 int3 1 = auto-negotiation lp acknowledge 0 = not source of interrupt ro/ lh 0 29.2 int2 1 = parallel detection fault 0 = not source of interrupt ro/ lh 0 29.1 int1 1 = auto-negotiation page received 0 = not source of interrupt ro/ lh 0 29.0 reserved ignore on read. ro/ lh 0 table 5.43 register 30 - interrupt mask address name description mode default 30.15:8 reserved write as 0; ignore on read. ro 0 30.7:0 mask bits 1 = interrupt source is enabled 0 = interrupt source is masked rw 0 table 5.44 register 31 - phy special control/status address name description mode default 31.15 reserved do not write to this register. ignore on read. rw 0 31.14 reserved 31.13 special must be set to 0 rw 0 31.12 autodone auto-negotiation done indication: 0 = auto-negotiation is not done or disabled (or not active) 1 = auto-negotiation is done ro 0
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 48 smsc lan8187/lan8187i datasheet 5.3 interrupt management the management interface supports an interrupt cap ability that is not a part of the ieee 802.3 specification. it generates an active low interrupt signal on the nint output whenever certain events are detected. reading the interrupt source register (register 29) shows the source of the interrupt, and clears the interrupt output signal. the interrupt mask register (register 30) enables for each source to set (low) the nint, by asserting the corresponding mask bit. the mask bit does not mask the source bit in register 29. at reset, all bits are masked (negated). the nint is an asynchronous output. 31.11 mii_clk_sel mii mode: 0 = mii clock of 25mhz. (default) 1 = can be written in mii mode to set the interface speed to 50mhz. rmii mode: 0 = invalid (do not clear this bit if in rmii mode) 1 = rmii clock of 50 mhz (default) note: defaults low (0) always in mii mode and high always in rmii mode. rw rmii/mii mode depnd?t 31.10 reserved reserved rw 0 31.9:7 gpo[2:0] general purpose output connected to signals gpo[2:0] rw 0 31.6 enable 4b5b 0 = bypass encoder/decoder. 1 = enable 4b5b encoding/decoding. mac interface must be configured in mii mode. rw 1 31.5 reserved write as 0, ignore on read. rw 0 31.4:2 speed indication hcdspeed value: [001]=10mbps half-duplex [101]=10mbps full-duplex [010]=100base-tx half-duplex [110]=100base-tx full-duplex ro 000 31.1 reserved write as 0; ignore on read rw 0 31.0 scramble disable 0 = enable data scrambling 1 = disable data scrambling, rw 0 interrupt source source /mask reg bit # energyon activated 7 auto-negotiate complete 6 remote fault detected 5 link status negated (not asserted) 4 auto-negotiation lp acknowledge 3 parallel detection fault 2 auto-negotiation page received 1 table 5.44 register 31 - phy special control/status (continued) address name description mode default
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 49 revision 0.6 (02-24-06) datasheet 5.4 miscellaneous functions 5.4.1 carrier sense the carrier sense is output on crs. crs is a signa l defined by the mii specif ication in the ieee 802.3u standard. the phy asserts crs based only on receive activity whenever the phy is either in repeater mode or full-duplex mode. otherwise the phy asserts crs based on either transmit or receive activity. the carrier sense logic uses the encoded, unscrambled data to determine carrier activity status. it activates carrier sense with the detection of 2 non-contiguous zeros within any 10 bit span. carrier sense terminates if a span of 10 consecutive ones is detected before a /j/k/ start-of stream delimiter pair. if an ssd pair is detected, carrier sense is asserted until either /t/r/ end?of-stream delimiter pair or a pair of idle symbols is detected. carrier is negated after the /t/ symbol or the first idle. if /t/ is not followed by /r/, then carrier is maintained. carrier is treated similarly for idle followed by some non-idle symbol. 5.4.2 collision detect a collision is the occurrence of simultaneous transmit and receive operations. the col output is asserted to indicate that a collision has been detected. col remains active for the duration of the collision. col is changed asynchronously to both rx_clk and tx_clk. the col output becomes inactive during full duplex mode. col may be tested by setting register 0, bit 7 high. this enables the collision test. col will be asserted within 512 bit times of tx_en rising and will be de-asserted within 4 bit times of tx_en falling. in 10m mode, col pulses for approximately 10 bit ti mes (1us), 2us after each transmitted packet (de- assertion of tx_en). this is the signal quality error (sqe) signal and indicates that the transmission was successful. the user can disable this pulse by setting bit 11 in register 27. 5.4.3 isolate mode the phy data paths may be electrically isolated from the mii by setting register 0, bit 10 to a logic one. in isolation mode, the phy does not respond to the txd, tx_en and tx_er inputs. the phy still responds to management transactions. isolation provides a means for multiple phys to be connected to the same mii without contention occurring. the phy is not isolated on power-up (bit 0:10 = 0). 5.4.4 link integrity test the lan8187/lan8187i performs the link integrity test as outlined in the ieee 802.3u (clause 24-15) link monitor state diagram. the link status is multiplexed with the 10mbps link status to form the reportable link status bit in serial management register 1, and is driven to the link led. the dsp indicates a valid mlt-3 waveform present on the rxp and rxn signals as defined by the ansi x3.263 tp-pmd standard, to the link monitor state-machine, using internal signal called data_valid. when data_valid is asserted the control logic moves into a link-ready state, and waits for an enable from the auto negotiation block. when received, the link-up state is entered, and the transmit and receive logic blocks become active. should auto negotiation be disabled, the link integrity logic moves immediately to the link-up state, when the data_valid is asserted. note that to allow the line to stabilize, the li nk integrity logic will wait a minimum of 330 sec from the time data_valid is asserted until the link-ready state is entered. should the data_valid input be negated at any time, this logic will immediately nega te the link signal and enter the link-down state. when the 10/100 digital block is in 10base-t mode, the link status is from the 10base-t receiver logic.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 50 smsc lan8187/lan8187i datasheet 5.4.5 power-down modes there are 2 power-down modes for the phy: 5.4.5.1 general power-down this power-down is controlled by register 0, bit 11. in this mode the entire phy, except the management interface, is powered-down and stays in that condition as long as bit 0.11 is high. when bit 0.11 is cleared, the phy powers up and is automatically reset. 5.4.5.2 energy detect power-down this power-down mode is activated by setting bit 17.13 to 1. in this mode when no energy is present on the line the phy is powered down, except for the management interface, the squelch circuit and the energyon logic. the energyon logic is used to detect the presence of valid energy from 100base-tx, 10base-t, or auto-negotiation signals in this mode, when the energyon signal is low, the phy is powered-down, and nothing is transmitted. when energy is received - link pulses or packets - the energyon signal goes high, and the phy powers-up. it automatically resets itself into the state it had prior to power-down, and asserts the nint interrupt if the energyon interrupt is enabled. the first and possibly the second packet to activate energyon may be lost. when 17.13 is low, energy detect power-down is disabled. 5.4.6 reset the phy has 3 reset sources: hardware reset (hwrst) : connected to the nrst input, and to the internal por signal. if the nrst input is driven by an external source, it should be held low for at least 100 us to ensure that the phy is properly reset. the phy has an internal power-on-reset (por) signal which is asserted for 21ms following a vdd33 (+3.3v) and vddcore (+1.8v) power-up. this internal por is internally ?or?-ed with the nrst input. during a hardware reset, either external or por, an external clock must be supplied to the clkin signal. software (sw) reset : activated by writing register 0, bit 15 high. this signal is self- clearing. after the register-write, internal logic extends the reset by 256s to allow pll-stabilization before releasing the logic from reset. the ieee 802.3u standard, clause 22 (22.2.4.1.1) states that the reset process should be completed within 0.5s from the setting of this bit. power-down reset : automatically activated when the phy comes out of power-down mode. the internal power-down reset is extended by 256s after exiting the power-down mode to allow the plls to stabilize before the logic is released from reset. these 3 reset sources are combined together in the digi tal block to create the internal ?general reset?, sysrst, which is an asynchronous reset and is acti ve high. this sysrst directly drives the pcs, dsp and mii blocks. it is also input to the central bias block in order to generate a short reset for the plls. the smi mechanism and registers are reset only by the hardware and software resets. during power- down, the smi registers are not reset. note that some smi register bits are not cleared by software reset ? these are marked ?nasr? in the register tables. for the first 16us after coming out of reset, the mii will run at 2.5 mhz. after that it will switch to 25 mhz if auto-negotiation is enabled.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 51 revision 0.6 (02-24-06) datasheet 5.4.7 led description the phy provides four led signals. these prov ide a convenient means to determine the mode of operation of the phy. all led signals are either active high or active low. the four led signals can be either active-high or active-low. polarity depends upon the phy address latched in on reset. the lan8187/lan8187i senses each phy address bit and changes the polarity of the led signal accordingly. if the address bit is set as level ?1?, the led polarity will be set to an active- low. if the address bit is set as level ?0?, the led polarity will be set to an active-high. the activity led output is driven active when crs is active (high). when crs becomes inactive, the activity led output is extended by 128ms. the link led output is driven active whenever the phy detects a valid link. the use of the 10mbps or 100mbps link test status is determined by the condition of the internally determined speed selection. the speed100 led outp ut is driven active when the operating s peed is 100mbit/s or during auto- negotiation. this led will go inactive when the operating speed is 10mbit/s or during line isolation (register 31 bit 5). the full-duplex led output is driven active lo w when the link is operating in full-duplex mode. 5.4.8 loopback operation the 10/100 digital has two independent loop-back modes: internal loopback and far loopback. 5.4.8.1 internal loopback the internal loopback mode is enabled by setting bit register 0 bit 14 to logic one. in this mode, the scrambled transmit data (output of the scrambler) is looped into the receive logic (input of the descrambler). the col signal will be inactive in th is mode, unless collision test (bit 0.7) is active. in this mode, during transmission (tx_en is hi gh), nothing is transmi tted to the line and the transmitters are powered down. 5.4.9 configuration signals the phy has 11 configuration signals whose inputs should be driven continuously, either by external logic or external pull-up/pull-down resistors. 5.4.9.1 physical address bus - phyad[4:0] the phyad[4:0] signals are driven high or low to give each phy a unique address. this address is latched into an internal register at end of hardware reset. in a multi-phy application (such as a repeater), the controller is able to manage each phy via the unique address. each phy checks each management data frame for a matching address in the relevant bits. when a match is recognized, the phy responds to that particular frame. the phy address is also used to seed the scrambler. in a multi- phy application, this ensures that the scramblers are out of synchronization and disperses the electromagnetic radiation across the frequency spectrum. 5.4.9.2 mode bus ? mode[2:0] the mode[2:0] bus controls the configuration of the 10/100 digital block.
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 52 smsc lan8187/lan8187i datasheet table 5.45 mode[2:0] bus mode[2:0] mode definitions default register bit values register 0 register 4 [13,12,10,8] [8,7,6,5] 000 10base-t half duplex. auto-negotiation disabled. 0000 n/a 001 10base-t full duplex. auto-negotiation disabled. 0001 n/a 010 100base-tx half duplex. auto-negotiation disabled. crs is active during transmit & receive. 1000 n/a 011 100base-tx full duplex. auto-negotiation disabled. crs is active during receive. 1001 n/a 100 100base-tx half duplex is advertised. auto- negotiation enabled. crs is active during transmit & receive. 1100 0100 101 repeater mode. auto-negotiation enabled. 100base-tx half duplex is advertised. crs is active during receive. 1100 0100 110 power down mode. in this mode the phy wake-up in power-down mode. n/a n/a 111 all capable. auto-negotiation enabled. x10x 1111
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 53 revision 0.6 (02-24-06) datasheet chapter 6 electrical characteristics the timing diagrams and limits in this section define the requirements placed on the external signals of the phy. 6.1 serial management interface (smi) timing the serial management interface is used for status and control as described in section 4.13 . figure 6.1 smi timing diagram table 6.1 smi timing values parameter description min typ max units notes t1.1 mdc minimum cycle time 400 ns t1.2 mdc to mdio (write) delay 0 300 ns t1.3 mdio (read) to mdc setup 10 ns t1.4 mdio (read) to mdc hold 10 ns mdc t1.1 t1.3 t1.2 valid data valid data t1.4 mdio (read from phy) mdio (write to phy)
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 54 smsc lan8187/lan8187i datasheet 6.2 mii 10/100base-tx/rx timings 6.2.1 mii 100base- t tx/rx timings 6.2.1.1 100m mii receive timing figure 6.2 100m mii receive timing diagram table 6.2 100m mii receive timing values parameter description min typ max units notes t2.1 receive signals setup to rx_clk rising 10 ns t2.2 receive signals hold from rx_clk rising 10 ns rx_clk frequency 25 mhz rx_clk duty-cycle 40 % rx_clk rxd[3:0] rx_dv rx_er t2.1 valid data t2.2
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 55 revision 0.6 (02-24-06) datasheet 6.2.1.2 100m mii transmit timing 6.2.2 mii 10base-t tx/rx timings 6.2.2.1 10m mii receive timing figure 6.3 100m mii transmit timing diagram table 6.3 100m mii transmit timing values parameter description min typ max units notes t3.1 transmit signals setup to tx_clk rising 12 ns t3.2 transmit signals hold after tx_clk rising 0ns tx_clk frequency 25 mhz tx_clk duty-cycle 40 % figure 6.4 10m mii receive timing diagram tx_clk txd[3:0] tx_en tx_er t3.1 t3.2 valid data valid data t4.1 t4.2 rx_clk rxd[3:0] rx_dv rx_er
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 56 smsc lan8187/lan8187i datasheet 6.2.2.2 10m mii transmit timing table 6.4 10m mii receive timing values parameter description min typ max units notes t4.1 receive signals setup to rx_clk rising 10 ns t4.2 receive signals hold from rx_clk rising 10 ns rx_clk frequency 25 mhz rx_clk duty-cycle 40 % receive signals setup to rx_clk rising 10 ns figure 6.5 10m mii transmit timing diagrams table 6.5 10m mii transmit timing values parameter description min typ max units notes t5.1 transmit signals setup to tx_clk rising 12 ns t5.2 transmit signals hold after tx_clk rising 0ns tx_clk frequency 2.5 mhz tx_clk duty-cycle 50 % tx_clk txd[3:0] tx_en t5.1 t5.2 valid data
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 57 revision 0.6 (02-24-06) datasheet 6.3 rmii 10/100base-tx/rx timings 6.3.1 rmii 100bas e-t tx/rx timings 6.3.1.1 100m rmii receive timing figure 6.6 100m rmii receive timing diagram table 6.6 100m rmii receive timing values parameter description min typ max units notes t6.1 rising edge of ref_clk to receive signals output valid 4ns t6.2 rising edge of ref_clk to receive signals output not valid 2ns ref_clk frequency 50 mhz ref_clk rxd[1:0] crs_dv t6.1 t6.2 valid data
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 58 smsc lan8187/lan8187i datasheet 6.3.1.2 100m rmii transmit timing 6.3.2 rmii 10base-t tx/rx timings 6.3.2.1 10m rmii receive timing figure 6.7 100m rmii transmit timing diagram table 6.7 100m rmii transmit timing values parameter description min typ max units notes t8.1 transmit signals setup to rising edge of ref_clk 4ns t8.2 transmit signals hold after rising edge of ref_clk 2ns ref_clk frequency 50 mhz figure 6.8 10m rmii receive timing diagram ref_clk txd[1:0] tx_en t8.1 t8.2 valid data valid data t9.1 t9.2 ref_clk rxd[1:0] crs_dv
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 59 revision 0.6 (02-24-06) datasheet 6.3.2.2 10m rmii transmit timing 6.4 ref_clk timing table 6.8 10m rmii receive timing values parameter description min typ max units notes t9.1 raising edge of ref_clk to receive signals output valid 4ns t9.2 raising edge of ref_clk to receive signals output not valid 2ns ref_clk frequency 50 mhz figure 6.9 10m rmii transmit timing diagram table 6.9 10m rmii transmit timing values parameter description min typ max units notes t10.1 transmit signals setup to ref_clk rising 4ns t10.2 transmit signals hold after ref_clk rising 2ns table 6.10 ref_clk timing values parameter description min typ max units notes ref_clk frequency 50 mhz ref_clk frequency drift +/- 50 ppm ref_clk duty cycle 40 60 % ref_clk jitter 150 psec p-p ? not rms ref_clk txd[1:0] tx_en t10.1 t10.2 valid data
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 60 smsc lan8187/lan8187i datasheet 6.5 reset timing figure 6.10 reset timing diagram table 6.11 reset timing values parameter description min typ max units notes t6.1 reset pulse width 100 us t6.2 configuration input setup to nrst rising 200 ns t6.3 configuration input hold after nrst rising 400 ns t6.4 output drive after nrst ri sing 20 800 ns 20 clock cycles for 25 mhz clock or 40 clock cycles for 50mhz clock t6.1 t6.2 t6.3 nrst configuration signals output drive t6.4
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 61 revision 0.6 (02-24-06) datasheet 6.6 dc characteristics 6.6.1 operating conditions vdd33 supply voltage +3.3v +/- 10% vddio supply voltage +1.6v to +3.6v operating temperature 0c to +70c industrial operating temperature -40c to +85c version available (lan8187i) 6.6.2 power consumption 6.6.2.1 power consumption device only power measurements taken over the operating conditions specified. see section 5.4.5 for a description of the power down modes. 1. current measurements do not include power applied to the magnetics. 2. current measurements do not include power applied to the optional external leds. 3. current measurements taken with vddio = +3.3v. table 6.12 power consumption device only mode 3.3v current (ma) 1.8v current (ma) i/o current (ma) total (ma) typical max typical max typical max typical max 10base-t /w traffic 16 tbd 21 tbd 2 tbd 39 tbd 100base-tx /w traffic 34 tbd 38 tbd 7 tbd 79 tbd energy detect power down 0.04 tbd 2.6 tbd 0.06 tbd 2.7 tbd
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 62 smsc lan8187/lan8187i datasheet 6.6.3 dc characteristics - i nput and output buffers table 6.13 mii bus interface signals name v ih v il i oh i ol v ol v oh txd0 vddio ? +0.4 v +0.5 v txd1 vddio ? +0.4 v +0.5 v txd2 vddio ? +0.4 v +0.5 v txd3 vddio ? +0.4 v +0.5 v tx_en vddio ? +0.4 v +0.5 v tx_clk -8 ma +8 ma +0.4 v vddio ? +0.4 v rxd0 -8 ma +8 ma +0.4 v vddio ? +0.4 v rxd1 -8 ma +8 ma +0.4 v vddio ? +0.4 v rxd2 -8 ma +8 ma +0.4 v vddio ? +0.4 v rxd3 -8 ma +8 ma +0.4 v vddio ? +0.4 v rx_er/rxd4 -8 ma +8 ma +0.4 v vddio ? +0.4 v rx_dv -8 ma +8 ma +0.4 v vddio ? +0.4 v rx_clk -8 ma +8 ma +0.4 v vddio ? +0.4 v crs -8 ma +8 ma +0.4 v vddio ? +0.4 v col -8 ma +8 ma +0.4 v vddio ? +0.4 v mdc vddio ? +0.4 v +0.5 v mdio vddio ? +0.4 v +0.5 v -8 ma +8 ma +0.4 v vddio ? +0.4 v nint/tx_er/txd4 vddio ? +0.4 v + 0.5 v -8 ma +8 ma +0.4 v 3.6v
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 63 revision 0.6 (02-24-06) datasheet table 6.14 lan interface signals name v ih v il i oh i ol v ol v oh txp see table 6.20, ?100base-tx transceiver characteristics,? on page 65 and ta b l e 6 . 2 1 , ?10base-t transceiver characteristics,? on page 65 . txn rxp rxn table 6.15 led signals name v ih v il i oh i ol v ol v oh speed100 vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v v ddio ? +0.4 v link vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v activity vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v fduplex vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v table 6.16 configuration inputs name v ih v il i oh i ol v ol v oh phyad0 vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v phyad1 vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v phyad2 vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v phyad3 vddio ? +0.4 v +0.5 v -12 ma +12 ma +0.4 v vddio ? +0.4 v phyad4 -8 ma +8 ma +0.4 v 3.7 v mode0 vddio ? +0.4 v +0.5 v mode1 vddio ? +0.4 v +0.5 v mode2 vddio ? +0.4 v +0.5 v reg_en vddio ? +0.4 v +0.5 v mii -8 ma +8 ma +0.4 v vddio ? +0.4 v
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 64 smsc lan8187/lan8187i datasheet note 6.1 these levels apply when a 0-3.3v clock is driven into clkin/xtal1 and xtal2 is floating. the maximum input voltage on xtal1 is vddio + 0.4v. table 6.17 general signals name v ih v il i oh i ol v ol v oh gpo0 -8 ma +8 ma +0.4 v vddio ? +0.4 v gpo1 -8 ma +8 ma +0.4 v 3.7 v gpo2 -8 ma +8 ma +0.4 v vddio ? +0.4 v nrst vddio ? +0.4 v +0.5 v clkin/xtal1 note 6.1 +1.40 v +0.5 v xtal2 - - nc table 6.18 analog references name buffer type v ih v il i oh i ol v ol v oh exres1 ai nc ai/o table 6.19 internal pull-up / pull-down configurations name pull-up or pull-down gpo0/mii pull-down gpo1/phyad4 pull-up mode0 pull-up mode1 pull-up mode2 pull-up test0 pull-down test1 pull-down speed100/phyad0 pull-up link/phyad1 pull-up activity/phyad2 pull-up fduplex//phyad3 pull-up nint/tx_er/txd4 pull-up nrst pull-up mdio pull-down mdc pull-down
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet smsc lan8187/lan8187i 65 revision 0.6 (02-24-06) datasheet note: for vddio operation below +2.5v, smsc recommends designs add external strapping resistors in addition the internal strapping resistors to ensure proper strapped operation. note 6.2 measured at the line side of the transformer, line replaced by 100 (+/- 1%) resistor. note 6.3 offset from 16 ns pulse width at 50% of pulse peak note 6.4 measured differentially. note 6.5 min/max voltages guaranteed as measured with 100 resistive load. rxd[3:0] pull-down rx_dv pull-down rx_clk pull-down rx_er/rxd4 pull-down txen pull-down col pull-down crs pull-down table 6.20 100base-tx transceiver characteristics parameter symbol min typ max units notes peak differential output voltage high v pph 950 - 1050 mvpk note 6.2 peak differential output voltage low v ppl -950 - -1050 mvpk note 6.2 signal amplitude symmetry v ss 98 - 102 % note 6.2 signal rise & fall time t rf 3.0 - 5.0 ns note 6.2 rise & fall time symmetry t rfs --0.5ns note 6.2 duty cycle distortion d cd 35 50 65 % note 6.3 overshoot & undershoot v os --5 % jitter 1.4 ns note 6.4 table 6.21 10base-t transceiver characteristics parameter symbol min typ max units notes transmitter peak differential output voltage v out 2.2 2.5 2.8 v note 6.5 receiver differential squelch threshold v ds 300 420 585 mv table 6.19 internal pull-up / pull-down configurations name pull-up or pull-down
high-performance mii and rmii 10/100 ethernet phy with hp auto-mdix datasheet revision 0.6 (02-24-06) 66 smsc lan8187/lan8187i datasheet chapter 7 package outline figure 7.1 64 pin tqfp package outline, 10x10x1.4 body, 12x12 mm footprint notes: 1. controlling unit: millimeter. 2. tolerance on the true position of the leads is 0.04 mm maximum. 3. package body dimensions d1 and e1 do not include the mold protrusion. maximum mold protrusion is 0.25 mm per side. 4. dimension for foot length l measured at the gauge plane 0.25 mm above the seating plane. 5. details of pin 1 identifier are optional but must be located within the zone indicated. table 7.1 64 pin tqfp package parameters min nominal max remarks a ~ ~ 1.60 overall package height a1 0.05 ~ 0.15 standoff a2 1.35 ~ 1.45 body thickness d 11.80 ~ 12.20 x span d1 9.80 ~ 10.20 x body size e 11.80 ~ 12.20 y span e1 9.80 ~ 10.20 y body size h 0.09 ~ 0.20 lead frame thickness l 0.45 0.60 0.75 lead foot length l1 ~ 1.00 ~ lead length e 0.50 basic lead pitch 0 o ~7 o lead foot angle w 0.17 0.22 0.27 lead width r 0.08 ~ ~ lead shoulder radius r2 0.08 ~ 0.20 lead foot radius ccc ~ ~ 0.08 coplanarity

▲Up To Search▲

Price & Availability of LAN8187-JT

	To Download LAN8187-JT Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .